Related to: #2050

Description

enable-auth and enable-route are not used by kserve. Therefore it's a bit odd to see enable-route: 'false' and have kserve create a route.

This change simply omits these annotations altogether unless their values are set to 'true'.

How Has This Been Tested?

• Deploy a kserve model.
• Inspect the ServingRuntime for the enable-auth and enable-route annotations to not be present.
• Similarly, create a model server. Disable route creation and auth.
• Inspect the ServingRuntime for the enable-auth and enable-route annotations to not be present.
• Create another model server. Enable route creation and auth.
• Inspect the ServingRuntime for the enable-auth and enable-route annotations to have values 'true'.

Test Impact

New unit tests.

Request review criteria:

Self checklist (all need to be checked):

• The developer has manually tested the changes and verified that the changes work
• Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

• Included any necessary screenshots or gifs if it was a UI change.
• Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

• The developer has tested their solution on a cluster by using the image produced by the PR to main